<html>
<body>
Reports calls to <code>Assert.assertEquals()</code>, <code>Assert.assertTrue()</code>, etc. methods
which can be migrated to Hamcrest declarative style <code>Assert.assertThat()</code> calls.
<p>For example:</p>
<pre><code lang="java">
  public class SubstantialTest {
    @Test
    public void testContents(Collection&lt;String&gt; c, String s) {
      Assert.assertTrue(c.contains(s));
      Assert.assertEquals(c, s);
      Assert.assertNotNull(c);
      Assert.assertNull(c);
      Assert.assertFalse(c.contains(s));
    }
  }
</code></pre>
<p>A quick-fix is provided to perform the migration:</p>
<pre><code lang="java">
  public class SubstantialTest {
    @Test
    public void testContents(Collection&lt;String&gt; c, String s) {
      assertThat(c, hasItem(o));
      assertThat(o, is(c));
      assertThat(c, notNullValue());
      assertThat(c, nullValue());
      assertThat(c, not(hasItem(o)));
    }
  }
</code></pre>
<!-- tooltip end -->
<p>This inspection requires that the Hamcrest library is available on the classpath.
<p>Use the <b>Statically import matcher's methods</b> option to specify if you want the quick-fix to statically import the Hamcrest matcher methods.
</body>
</html>